Method for communicating structured information

ABSTRACT

The method for communicating structured information, for a example a report or an account, between a first user and at least one second user includes a step of defining a document standard, which determines the general frame of the document in the form of a series of titles and/or conventional meanings and authorized values of certain conspicuous information fields. The transmitting user inputs data to be supplied incorporating a step of inputting text and/or titles as a supplement to the general frame and/or a step of selecting values on the conspicuous fields and transmitting data of the document addressed to the second user. Each recipient user selects a sorting criterion based on the titles or conspicuous fields. The document is then reorganized in accordance with the selected criterion and a step of supplying to the second user the document reorganized in accordance with the criterion.

RELATED U.S. APPLICATIONS

Not applicable.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

REFERENCE TO MICROFICHE APPENDIX

Not applicable.

FIELD OF THE INVENTION

The present invention concerns a method for communicating structuredinformation, notably by the generation, transmission and processing offiles making it possible to generate documents. It applies, inparticular, to the monitoring of activities using regular activityreports in a human organization, such as an industrial or administrativeorganization, or using meeting reports.

BACKGROUND OF THE INVENTION

In the following description, “reporting” is hereinafter used to referto the communication of reports or statements between persons of thesame organization, and, in particular, the communication of regular orroutine statements. The reporting can be done in numerous ways:

-   -   ascending or descending (relative to a hierarchy of decision        levels),    -   hierarchical or functional, oriented by “cost center” or profit        center”,    -   individual, collective, or “circulating”,    -   periodic (from daily to annual), or at the occurrence of the        particular events,    -   more or less formalized.

A part of the reporting involves quantitative elements that can beproduced in an automatic manner by an information system: costs, values,durations, trends, various indicators coming from ERP software (acronymof “Enterprise Resource Planning” for the planning of enterpriseresources), CRM (acronym of “Consumer Relation Management” formanagement of the client relation), and other functional help tools forthe organization. But most important is the reporting exchanged betweentwo persons (or groups of persons), such that they can communicate in aregular manner in the context of their respective roles. It is spokenhere of descriptions of facts, problems, requests, intentions,interpretations of numerical data. etc, of all qualitative informationwhich is necessary for the functioning of the human organization, andwhich in the end comprises expression and explanation.

Reporting is thus a significant function of any organization. Thisfunction, however, in the current state of the art, is both costly andpoorly equipped, though it has benefited from bureaucratic provisionsand electronic mail.

The technical problems that the present invention intends to solveinvolve the speed of the generation and supply of reporting information,on the one hand, and the quality and readability of the informationtransmitted between persons, on the other hand.

A report is costly to produce, in particular, because the editor spendsa lot of time on the tasks of presentation, sorting, and page layout,instead of on the expression of content, and this regardless of the toolused. This increased cost for formatting slows the preparation andtransmission of reports and thus impairs the speed of monitoring of theorganization. This increased cost can also lead the editor to sacrificecontent, simply because the editor devotes himself for a time,consciously or not, to this routine task. The quality of the informationis thus affected.

The readability of these reports is a second technical problem that thepresent invention intends to resolve. In fact, even if the editor takesgreat care in the presentation of his report (to the detriment of themonitoring speed), this presentation often has need to be revised by theaddressee depending on his own context, software and/or equipment(e-mail, printing driver, different page formats in the United Statesand in Europe, for example) from his choices or reading habits and fromhis own need to make a report of his activity, for himself or for otherswho, for their part will have to revise this report for their own needs.

The addressee of a report often has preferences on the presentation ofinformation: in which order, with which level of detail, and accordingto which conventions they must be presented. But there is no practicalway to encourage or facilitate the use of these standards by theissuers, apart from the implementation of a specific tool (text model orform), a costly and often ineffective solution because it is too rigid.

When these standards are defined, it is rare that they coincide with theones that the issuer would naturally use. The points of view aredifferent. For example, a worker would design his activity report in asequential manner (according to the list of processed tasks), while hismanager would want to see grouped on the one hand, the main results, andon the other hand, the points requiring his intervention. In this case,regardless of the quality of the applied standards, one of the two willbe restricted, and constrained by a “translation” force.

The readability and usability of the reports are thus limited in thecurrent state of the art.

The present invention intends to correct these disadvantages.

BRIEF SUMMARY OF THE INVENTION

For this purpose, the present invention intends, according to a firstaspect, a method for communicating structured information, for example,a report or statement, between a first user and at least one seconduser, characterized in that it consists of:

-   -   a step for defining a document standard, which determines the        general framework of the document in the form of a series of        titles and/or conventional notifications and values authorized        by certain fields of noteworthy information;    -   a step for inputting, by the first user, information to be        provided incorporating a step for inputting text and/or titles        as a supplement to the general framework and/or a step for        selecting values on the noteworthy fields;    -   a step for transmitting the information of the document from the        first user to the destination of each secondary user;    -   a step for selecting, by each secondary user, a sorting        criterion based on the titles or the noteworthy fields;    -   a step for re-organization of the document according to the        selected criteria; and    -   a step for supplying to the secondary user the document        re-organized according to the criterion.

By these arrangements, the inputting of the report is agreeable to thefirst user, the sender, and frees him from formatting constraints, whileconforming to the desires of each secondary user, or addressee, andcontaining all the information necessary for good communication betweenthe users, using the implemented standardization.

In fact, the inputting of the report is agreeable for the first user,the sender, because it makes use of zones of text to enter, in a ratheropen manner, the content of information that corresponds to the titlesdefined by the standard of the document or by himself. By the definitionof an interface, the sender is freed from the constraints of formatting.Moreover, since he can choose an automatic re-organization of theinformation, each secondary user renders the document according to hisneeds.

The implementation of a standard is a factor of mechanical effectivenessfor the reporting process: on the one hand, it defines the common ruleswhich must improve the quality and the completeness of the information,and makes everyone's reports so that they can be interpreted by all; onthe other hand, it opens various possibilities for automatic processing,presented at a later point. But this does not restrict expression, nordoes it reduce its human dimension. The personalization of the standardsmakes it possible to cover at the same time a large variety ofprofessions or organizations, and various more or less precise andstructured modes of reporting. The user can easily define them himselfwithout any outside help.

One of the advantages of the present invention is to make thisstandardization attractive by maximizing its profit and minimizing itsdisadvantages.

It is understood that the implementation of the present invention makesthe generation and use of information documents of the report orstatement type pleasant, rapid, economical, and effective.

Moreover, if the addressee user makes use of a standard, thetransmission of information can be limited to information that isdifferent from what is defined in the standard, which reduces theconsumption of resources for transmission and storage of documentinformation. The present invention can thus allow, in variations, theinformation of a document to be compressed while allowing a largefreedom for generation of documents and use of these documents.

According to the specific characteristics, during the step for inputtingand/or during the step for supplying, in at least one zone of text, thetitles defined by the standard and the text input by the user appear asa single line of text within the traditional ergonomics of the textprocessing. By these arrangements, each user is in a familiarenvironment for text processing.

According to the specific characteristics, during the step for definingthe standard, for at least one title, a selection step is made if thetitle can be modified by the first user during the inputting step. Bythese arrangements, the document can, in certain cases, be integrallymodified, for its textual part, by the user and transmitter, and inother cases, it can have titles suitable in advance which can not bemodified.

According to the specific characteristics, during the step for inputtingof the information, the first user can modify at least one part of thestandard defined during the step for definition of the standard. Bythese arrangements, the flexibility of modification of the document isincreased for the user and transmitter.

According to the specific characteristics, during the step fortransmission, the information of the document is transmitted accordingto an accessible page format over an information network, readable usinga web navigator and printable from any office work station equipped witha web navigator and a printer.

By these arrangements, the reception and use of the document can be doneby any computer equipped with a navigator over the information network,for example, the internet.

According to the specific characteristics, the method as succinctlyexplained above comprises a step for consolidation of documents, duringwhich the information of the documents which are linked to the sametitles are juxtaposed under a unique title into different documents tobe consolidated. Using these arrangements, the user and receiver canconsolidate several documents to make a synthetic document and analyzethe similarities and the differences between the documents which aretransmitted to him.

According to the specific characteristics, the method as succinctlyexplained above comprises a step for determining a summary of thedocument, during which information is selected as a function of ahierarchy of information values. By these arrangements, the user andreceiver can very rapidly comprehend the general content of thedocument.

Other advantages, goals, and characteristics of the present inventionemerge from the description that follows, made with regard to theattached drawing, in which FIG. 1 shows an organizational diagram of thesteps taken in a particular embodiment mode of the present invention.

The method that is the object of the present invention is preferentiallyimplemented in the form of a software which can be downloaded orinstalled on a computer from a medium such as a diskette or compactdisc. This computer generates files representing reports that can betransmitted to other computers by means of the media or the informationnetwork. In the particular embodiment modes, this computer is linked tothe sources of the information, for example, databases or sensors ofphysical variables such as the time, product quantities, which supplyinformation integrated into the report.

The method that is the object of the present invention makes possiblesimultaneously the implementation of a standardization of documents, anda personalization of the standard used. The tool that implements themethod that is the object of the present invention is not “structuring”.On the contrary, it integrates itself into an existing context (mode ofwork, office equipment, information system), even if this context isheterogeneous.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 shows an organizational diagram of the steps taken in aparticular embodiment mode of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

Before describing the drawing, a functional description of the steps forimplementing the invention is given here.

I/ Data Model

The definition of a standard is supported by a data model. In fact,regardless of its type and its context, a reporting document, “report”or statement, may be characterized by:

-   -   a set of meta-data that defines the context, the type, the        identity and the heading of the report:        -   name of the organization, periodicity, and role, addressee        -   sender(s), date and associated event, title        -   possibly, key words or other classification criteria    -   a list of information elements (or “items”), which comprise the        body of the report. These information elements can be        hierarchical, with any number of levels, even if in practice it        is rare to go beyond 2 or 3 levels of overlapping.

Each of these information elements is defined by:

-   -   an “author” (one who has defined or given information about the        information elements involved). This attribute is found to be        useful in the case of a collective or circulating report.    -   a “title” which characterizes the subject that is treated. In        the case of hierarchical information elements, the title of an        information element comprises a specification (a “sub-chapter”)        of information elements of an upper level.    -   a “priority” which characterizes the weight that the editor        wishes to assign the information elements. It can represent, for        example, a degree of importance (Routine, To Be Noticed,        Critical), or a degree of urgency, or a combination of the two.        But the use and the codification of this priority are by        convention, and can vary from one context to another.    -   a “category” which characterizes either the type of information        supplied by the information elements, or the area of concern to        which the information element refers. For example, it indicates        whether the status of a job, a problem, a request, an indicator,        a contact, etc. is involved, and/or if a project, a team,        methods, etc. are discussed. However, this is a non-restrictive        list, the typology can be specific to the profession, the role        or the functioning mode of the entity involved.    -   possibly, a scalar “value” (number, date, indicator of status,        etc.), for which the format and the signification depend on the        “type” or “domain” of the information element.    -   one or more paragraphs of free text, making it possible to        detail the information as much as necessary.

It is noted that the information elements of all hierarchical levels aremodeled in the same manner. Thus, an information element having a higherlevel (or intermediate level) in the hierarchy can be reduced to a“Title”, but one may also consider it to be of interest to link acategory or value to it, giving, for example, general information on theset of subjects that it covers.

II/ Definition of the Standard

The definition of the standard reflects the context in which thedocuments are exchanged, the objective of the documents, and theconventions used in order to describe useful information in them. Everyeditor can, if he or she desires, define his or her own standards foreach document. But the standards only have real interest if they areapplied by the group of contributors and in a relatively stable mannerover time. In general, the standards will be thus defined by one of theusers (or by a representative of them having the authority to do it), inorder to be then applied by all the editors and for all the documentsinvolved.

This definition is made using a specific function of the tool, for whichthe result is a “file for definition of the standard”, an autonomoustransportable file that can then be transmitted to the editors by commonmeans.

The definition of a standard comprises four phases that can be executedin any order:

1/ The definition of the general attributes of the document that figurein an invariant manner in the heading of the documents: name of theaddressee entity of the document and/or the upper level entity to whichit pertains, code and title designating the function of the document(for example, “RHEBDO” and “Weekly Report”), periodicity or unit ofdating the document (“DAY”, “MONTH”, TRIMESTER”, “YEAR”, “EVENT”), andpossibly a list of addressees of the document (when it is fixed). Thedefinition of these elements is done using one page of traditionaldialog of the form type.

2/ The definition of “priorities”, i.e. the values authorized for the“priority” field of the information elements of the document. The numberof “priorities” is not limited, though in practice it is estimated thata number greater than 5 would present little interest.

Each of these “priorities” is defined in the file representing adocument according to a standard, by:

-   -   a short alpha-numeric text (typically, less than 10 characters);    -   in an optional manner, an icon selected in the tool's library of        icons. This icon can substitute for the text code of the        priority in the visual representation of the document;    -   any number which will determine the sorting order of the        information elements in the “by priority” view;    -   a Boolean (YES/NO) which determines whether an item having the        priority involved must appear in the summary of the document;    -   a descriptive text, designed to recall to the editor of a        document the conventional importance of this priority. This text        will be presented to the editor during the selection of a        priority.

The definition of the “priorities” is made using a display of the tabletype, by vertical scrolling, in which the user can directly insert orremove lines, and modify values of the field using the keyboard (forfields having an open value) or using selected dialog boxes (for thefields having a domain of limited values).

In the illustration given with regard to the tables below, the standarddefines three priority levels:

-   -   “CRITICAL” code, “CRITICAL” icon, number 0,    -   “Note” code, “DANGER” code, number 5,    -   ““(blank) code, no icon, number 10.

3/ The definition of the “categories”, i.e. the values authorized forthe field “category” of the information elements of the document. Thenumber of “categories” is not limited. Each of these “categories” isdefined by:

-   -   a short alpha-numeric text (typically, less than 10 characters);    -   any number which will determine the sorting order of the        information elements in the “by priority” view;    -   a Group name, which makes it possible to group several        categories in a same section of the document during sorting “by        category”;    -   a Boolean (YES/NO) which determines whether an item having the        category in question must appear in the summary of the document;    -   an indicator, chosen from (“NUMBER”, “PERCENT”, “SELECTION”,        “NONE”, and “OPEN”) which determines the type expected for the        field “value” of the information elements having the category in        question;    -   a Boolean (YES/NO) indicating whether the field “value” is        required for the information elements having the category in        question;    -   a descriptive text, designed to recall to the editor of a        document the conventional importance of this priority. This text        will be presented to the editor during the selection of a        priority.    -   an optional list of “detail paragraph labels”. For each of them,        it can be specified if it can or can not be modified or removed        by the editor;    -   when the indicator of the type of value is “SELECTION”, a list        of values possible for the Value attribute of the information        elements having the category in question.

For each of these possible values, one defines:

-   -   a short text code (typically, less than 10 characters),    -   in an optional manner, an icon selected in the tool's library of        icons. This icon can substitute for the text code of the value        in the visual representation of the document;    -   any number which will determine the secondary sorting order of        the information elements in the “by priority” view;    -   a Boolean (YES/NO) which determines whether an item having the        category in question must appear in the summary of the document;    -   a descriptive text, designed to recall to the editor of a        document the conventional importance of this priority. This text        will be presented to the editor during the selection of a value        for an item having the category in question.

The definition of these five elements is done using a page of thespecific dialogue containing:

-   -   a main table, by vertical scrolling, of the same principle as        that of the “priorities”,    -   for the paragraph labels and the authorized values, two        secondary scrolling tables for which the content is linked to        the category selected in the main table.

In the drawing given in regard to the tables below, the standard definessix categories:

-   -   “general status” (GLOBAL group): The possible values are “GOOD”,        AVERAGE”, and “BAD”, and the associated icons represent        respectively an arrow facing upwards, horizontal, and downwards;    -   “Job” (JOB group): The associated value is a percentage and an        associated detail paragraph is named “Status”;    -   “PB/Technique” (PROBLEMS group): No associated value and two        associated detail paragraphs are named “Impact” and “Action”;    -   “PB/Resources” (PROBLEMS group): No associated value and there        is no specified detail paragraph;    -   “RQ/Act” (REQUESTS group): The possible values are “Rapp” (for        “Reminder”) and “URG” (for “urgent”) and there is no specified        detail paragraph;    -   “RQ/Meeting (REQUESTS group): The possible values are “Rapp” and        “URG” (for “urgent”) and there is no specified detail paragraph.    -   4/ The definition of a document framework, i.e. a list of        information elements for which only the titles and the        categories are defined. During the creation of a document        according to the standard in question, this framework comprises        the initial status of the document. The definition of this        document framework is done exactly like the inputting of a        document, except that:    -   the “value” field and the text of the detailed paragraphs can        not be input,    -   an additional command makes it possible to specify, for each        information element, if it can or can not be removed and if its        title and its category can or can not be modified during the        editing of a document.

III/ Use of a Standard.

During the creation of a document, the selection of the standard to beapplied is done by designation of a “standard file”, either by a commandparameter for starting the tool, or by pointing in a dialog box afterthe tool has been started.

The reader is reminded that the embodiment mode described and shown isbased on a standard example (categories “General Status”, “Job”, etc.,and associated classification groups) but that other standard examplescan be implemented while remaining in the field of the presentinvention.

IV/ Creation of a Document

The creation of a document comprises:

-   -   An initial phase which consists in selecting a “standard file”,        by a dialog box. The program initializes the content of the        document on the basis of the standard file selected, notably        with the “document framework” defined by the standard, if there        is one.    -   A definition phase of the various general attributes: name and        initials of the editor, code and name of the entity to which he        belongs or in the name of which he is writing, date (according        to the unit of dating defined by the standard). These data can        be keyed by the editor, but they can also be supplied        automatically by the program, on the one hand, as a function of        the current date, on the other hand, as a function of the        identification data of the editor stored at his work station.    -   A phase for release of the content. This release of content is        done by the inputting of the text, combined with the menu        commands or buttons, according to a function that is very        similar to that of a text processing software. Using the mouse        and/or keyboard, the user can position the cursor at any        position in the document in order to add or remove text, and        select the portions of text (characters, words, paragraphs or        whole items to change them or remove them.

With regard to the processing of the text, there is however, numerousdifferences, and, in particular, in a particular embodiment mode that isthe object of a prototype, the following differences:

-   -   The selections of the formatting are reduced. There is no        control for page setting, nor indentation, or numbering of the        titles, these operations being done automatically and in real        time by the program. With regard to the fonts used, the user can        specify only the family and the size of the characters (applied        globally to the document, for its visual or printable form), the        other attributes (boldface, italics, spacing) being determined        by the program according to the placement of the text;    -   The traditional editing commands “Cut/Copy/Paste” are limited:        they can only involve the portions of the title, or the detail        paragraphs, or one or more whole information elements;    -   There are specific commands taking into account the structured        character of the text, in order to lower/raise the level of the        title of an information element (i.e. combine their contents        under the same title), transform a detail paragraph into an        information element, modify the label of a detail paragraph;    -   The “priority” and “category” fields of each information element        can be entered either via the keyboard, or by selection in a        menu (“pop-up menu”). The same applies for the “value” field of        information elements for which the category defines a finished        list of possible values;    -   The “author” field is entered automatically, as a function of        the computer and/or the open session on the computer, or the        data supplied at the installation of the software that the        present invention implements.

It is observed that the term “title” can apply to two things: on the onehand, the names of information elements (in the tables “Project ALPHA”,“Project BETA”), on the other hand, the labels associated with detailparagraphs of an information element (“Status:”; “Impact:”). The firstcan be defined in the standard, in the form of a framework of thepre-defined report. The second ones are also defined in the standard, inthe sense that they are associated with a “category”, and that when thiscategory is selected by the editor for information elements, the toolautomatically creates one or more detail paragraphs with these labels.In the two cases, it is also the standard that determines whether these“titles” can be modified or not or removed by the editor.

The creation of a document ends with the saving of the document in theform of an XML file, to be sent to the addressees or for storage inanticipation of later modifications. Also, at any instant, one cangenerate an “image HTML” of the document, in the form of an HTML file,which can then be printed, transported or inserted into the body of ane-mail depending on the information infrastructure available to theuser.

V/ Modification of a Document

The modification of an existing document is done simply by reloading thedocument file, preferably according to the XML language, received orsaved during a previous session, then by the application of editingoperations described above. However, there are some nuances which dependon the function options of the tool (selected during the command tostart the program, or by dialog after starting):

-   -   One option makes it possible to protect (i.e. prevent the        removal or modification of) all information elements whose        author is another person than the one making the modification of        the document.    -   One option makes it possible to preserve the track of the        content before each modified information element, for the        “category” and “value” fields, and to make the initial value of        these fields appear, in addition to the modified value, with a        particular design which highlights the modification.    -   One option makes it possible to consider the loaded document not        as a document to be modified, but as a “model” which serves to        initialize the content of a new document.

In its initial version that is the object of the prototype developed bythe inventor, the method that is the object of the present invention isan autonomous executable, installed directly at the work station of theuser (PC Windows, registered trademarks, and eventually, Linux,registered trademark). Each document is thus an independent file,structured in the XML format, and in this manner, displayable andprintable by any Internet navigator equipped with the proper paperstyle. But, it is also possible to generate an HTML document in atotally self-sufficient manner. The report files (XML or HTML) can betransported by an electronic mail system of any type. The file thatdefines the standard, normally defined by the addressee of the reports,will be transmitted to the editors by the same means.

Eventually, another implementation of the method that is the object ofthe invention is designed to be integrated into the communicationinfrastructure of the users, in order to be directly accessible fromtheir “collaborative” environment (MS-Outlook type or Lotus, registeredtrademark). The documents will then be objects managed by thisinfrastructure, under the title of “messages”, “jobs”, “rendezvous”,etc.

The primary table, below, shows the structure of the data, according tothe XML language as managed by the object method of the invention. Init, one observes a series of information elements, each informationelement being represented on a line and comprising the following fields:

-   -   “BF” which represents an incremental number for information        inputting;    -   “Sign” which represents an identification of the author of the        information element;    -   “Date” which represents the creation date or the last        modification of the information element;    -   Three fields which represent the priority degree (in the sense        defined in the data model) affected by the information element        by the editor:        -   “Priority”: text code appearing in the document,        -   “Priol”: numerical value used in order to classify the            information elements by priority,        -   “Priolcon”: name of the icon displaying the priority, as an            alternative to the text code defined by “priority”;    -   “Category” which represents the category of the information        element (in the sense defined in the data model);    -   “C” which represents, in a numerical manner, the category        indicated in the preceding column;    -   “CatGroup”, which represents the category group in which the        information element will be classed, during the reorganization        “by category”. This makes it possible to combine several        “categories” in the same category group;    -   Three fields which represent the “value” (in the sense defined        by the data model) linked to the information element by the        editor:        -   “Cvalu”: text representation (inputting), which can be a            number or a text symbol, according to the category of the            information element,        -   “ValR”: in the case of a non-numerical value, numerical            expression of the value for sorting “by value”;        -   “Valcon”: name of the icon displaying the value, as an            alternative to the text code defined by “Cvalu”;    -   “Highlight” which shows the fact that the information element        has been “highlighted” by the editor.

It is observed that the information elements of the second level arelinked to projects that are information elements of the first level, bythe hierarchy of “titles”. In internal representation, the “title” of aninformation element is comprised of one or more elements, the ones shownin the secondary table at the bottom left (Tindex/PT). This “title” isalways complete, i.e. it contains the title of the information elements“parents”, i.e. the upper level of the information element involved. Inthe visual display of the document, these titles can appear, as afunction of the sorting mode selected and/or the preferences of theuser:

-   -   either in the complete form (“complete” titles),    -   or in the incremental form (hierarchical titles).

The three tables at the bottom of the table below show “detail” tables(in the sense of the SGBD terminology), i.e. the structures of the listinside an information element pointed to by a pointer (placed here online number 5), in the event of:

-   -   the list of elements having an upper level title (see above) of        the information element in question, to the left,    -   the list of “paragraph labels” of the information element in        question, a paragraph being a title having a lower level, in the        middle,

for each paragraph of the information element in question, the list oflines of text of the paragraph, to the right. BR Sign Date PriorityPriol Priolcon Category C CatGroup CValu ValF Valcon Highlight 0 ML Aug.08, 2002 10 General Status 1 Global Avg. 1 Aright None 1 ML Aug. 08,2002 10 Job 2 Jobs 90% −1 None 2 ML Aug. 08, 2002 10 Job 2 Jobs 60% −1None 3 ML Aug. 08, 2002 Note 5 Danger Pb/Tech 3 Problems −1 None 4 MLAug. 08, 2002 10 RQ/Meeting 4 Requests Rapp 1 None >5   ML Aug. 08, 200210 Job 2 Jobs 20% −1 None 6 ML Aug. 08, 2002 Critiqu 0 Critical RQ/Act 4Requests Urg 0 None 7 ML Aug. 08, 2002 10 Job 2 Jobs 10% −1 None 8 MLAug. 08, 2002 10 Job 2 Jobs  0% −1 None 9 ML Aug. 08, 2002 Critiqu 0Critical PB/Resources 3 Problems −1 None 10  ML Aug. 08, 2002 10 GeneralStatus 1 Global Good 0 Arup None 11  ML Aug. 08, 2002 10 Job 2 Jobs 20%−1 None Tindex PT Project DetTitle P >1   Project Alpha Status This textexplains the advancement of the job “Financing” of the project

Concretely, the method that is the object of the present inventionallows a standardization along three themes:

-   -   The definition of the various “categories”, in the sense of the        model described above. These categories must represent the        different types of information elements that one would like to        be able to use as a sorting or grouping theme. For each        information element of the report, the editor must choose one of        these categories. This choice can condition the format of the        “value” field, and automatically create paragraphs of text with        pre-defined labels, or titles, in order to orient the editor.    -   the codification of the “priority” (in the sense described        above), in a graphical, symbolic or numbered manner. The        standard will be freely defined and in as many degrees as        necessary in giving them the conventional signification best        adapted to the context.    -   Possibly, the definition of a framework of content, in the form        of a “summary” (list of information elements, hierarchical or        not). The editor can enter this framework, but also modify it or        complete it as he pleases.

The automatic formatting help can appear to be a superficialcharacteristic, but its functions will be the first ones observed by theusers, and they play an important role in the communication of thereports:

-   -   Free the editor completely from all constraints customary in        formatting text: heading, numbering, indentation, graphics        emphasis, and page layout.    -   Automatically produce an agreeable and effective visual        appearance, which adapts itself to the work environment (screen        and printer) of the sender and addressee.    -   Make easier the input of the data using the selection lists or        other functions for assistance in inputting, directly exploiting        the standards defined by the addressee.    -   While preserving ergonomics and flexibility of traditional        linear text processing (as opposed to a form), in which the user        has all freedom of expression beyond standards, and always sees        a “printable” result.

As shown in the second to eighth tables, above, using the method that isthe object of the present invention, the addressee of a series ofreports can immediately do three jobs:

-   -   The individual chronological monitoring of each report: the jobs        in progress are they progressing normally, are the problems        regulated, what are the new elements, . . . etc. It is in this        exercise that a manager can detect hidden problems, which the        sender himself may not be aware of: abnormal deviations, chronic        dysfunction, useless efforts, etc.    -   The “consolidation” or “concatenation” of the different reports,        notably when several senders have contributed to the same        business and each gives his point of view and added value.        Within a team, this job is the key to the coordination and the        resolution of local conflicts. For its relations with the        outside, it gives a manager a complete and reliable vision of        the business handled.    -   The synthesis, an often intuitive exercise in which everyone        applies his personal criteria. Very often, for a hierarchical        manager, this involves identifying, on the one hand, the points        which require his intervention, on the other hand, those points        likely to be of interest to his upper level manager. From that        he will derive his action priorities and his own reporting.

In the second table below, a first example is observed of thepresentation of a first document organized by subject, as appears on acomputer screen. This presentation is displayed here by an Internetnavigation software program such as Internet Explorer (registeredtrademark of Microsoft Corp., registered trademark), it is similar tothe one displayed by the program implementing the method that is theobject of the present invention, itself in the phases of editing orconsulting of the document. The document contains meta-information, anindication of the organization of the presentation of the document, here“view by subject” and eleven zones for giving information elements, thefirst nine, at the top of the page, involving the subject “BETAproject”, based on organization by subject indicated by the notice “viewby subject”. Each information element corresponds to a horizontal zonewhich extends into all zones of the subject involved.

The meta-information contains a company name “Systeam” and thedepartment, abbreviated: “DT” and in full: “Technical Management” towhich the editor belongs, the name of the abbreviated report “TEST” andin full: “Test report”, the date or subject of the abbreviated report“W28” and in full: “week 28”, and the sending entity or the oneinvolved, abbreviated “BRDEV”, and in full: “Group Project Beam-Report”.

To the left, the zones for information each contain two columns. In thecolumn that is furthest to the left, the author of the informationelement is indicated, in the form of initials, here “ML”. Thisinformation comes from the field “Sign” shown in the table above. In theone of the two columns which is furthest to the right, the degrees ofurgency and priority are shown, an absence of information indicatingthat there is no particular urgency, an exclamation point (not shown inthe table) in a triangle indicating that there is a moderate urgency andan exclamation point in bold (not shown in the tables) in a squareindicating a high degree of urgency, danger or priority. Thisinformation comes from the field “Priority” or “Priol” shown in thefirst table above.

In the center, the information zones, the most extended in width sincethey cover more than half of the width of the page, contain elements inboldface, called “titles” which can or can not be modified by the useraccording to the standard applied, and elements in thin characters thatthe user can edit, i.e. modify by typing text, copying, pasting,cutting.

In the second table below, one observes that the titles and theinformation supplied or edited by the user only form a single continuoustext without a separator, frame, horizontal line. The titles form titlesand subtitles and the information supplied by the user of the text body.The user thus finds himself in a familiar environment of textprocessing.

To the right of the central information zones, the category ofinformation element is indicated in the form of frames containing, forexample, the terms “General Status” corresponding to the term “global”in the field “CatGroup” shown in the first table above, “Job”, RqMeeting” corresponding to the term “Request” or “Pb Technique”corresponding to the term “Problem”. Finally, at the extreme right ofthe pages, information zones are located which, according to thedocument standard, contain icons in the form of arrows when theinformation element has the term “General Status” in the zone to theimmediate left, indications of the percentage when, in the zoneimmediately to the left, the term “Job” or terms such as “Rep” or “Urg”are located which come from the field “CValu” shown in the above table.

It is understood that the arrow indicates the general progression of thesubject involved while the percentages indicate the degree ofrealization of the corresponding job. File Edition Display FavoriteTools ? SYSTEAM Technical Management DT Report TEST Test Report ObjectW28 Week 28 From: BRDEV Group Project Beam Report Notes: View by SUBJECTPROJECT ALPHA ML 1.  Project ALPHA General status Δ    This textexplains the general status of project ALPHA,    from the point of viewof ML ML 1.1 Development Job 60%    Status: This text explains theprogress of the job    “development” of the project ALPHA ML Δ    > Bugin XML function interface PB/Technical    Impact: This text describesthe consequences of the    problem “Bug in the XML function interface”ML      Use of a different supplier? RQ/Meeting Rapp      This textproposes a meeting date to examine a      proposal for a solution to theproblem “Bug in      XML function interface” ML 1.2 Financing Job 20%   Status: This text explains the progress of the job    “financing” of theproject ALPHA ML □    > Start over Devis Industrialization RQ/Act URG     This text states the reason for action demanded      from theaddressee of the report ML 1.3 Marketing Job 10% ML    > ContactDistributor Job  0%    Status: This text explains the progress of thejob    “marketing” of the project ALPHA ML □    > General delayPB/Resources    This text emphasizes the delay in the marketing jobs,   attributing the cause to the lack of qualified human    resources andspecifies the need to be met PROJECT BETA ML 2.  Project BETA Generalstatus H    This text explains the general status of project BETA,   from the point of view of ML ML 2.1 Definition of the Product Job 20%   Status: This text explains the progress of the job    “definition of theproduct” of the project BETA

By a simple main menu command of the software implementing an embodimentmode of the method that is the object of the invention or by a mouseclick on the title of the corresponding column, it is possible tore-organize the sequence of information elements to the request, as afunction of a specified sorting and grouping theme:

-   -   by “subject”. It is often in this form that the report will be        initially input, but this is not mandatory.    -   by “category”, with the possibility for secondary sorting        according to the “value”.    -   by “priority”.    -   by “author” (for example, for a collective or circulating        report).    -   on a personalized criteria, based on a complex combination of        these fields.

The display of the “titles” is modified as a result: once an informationelement is detached from the hierarchical upper-level informationelement, its title must be completed in order to position it in anabsolute manner.

Below, a second example is shown of the presentation of the firstdocument shown above, but re-organized by category, as it would appearon a computer screen. This presentation is also displayed here by anInternet navigation software program. The document containsmeta-information, an indication of the organization of the presentationof the document, here “view by category” and eleven zones for givinginformation elements, the first two, at the top of the page, involvingthe category “Global”, the five following, the category “Jobs”, the nexttwo the category “Problems”, and the last two at the bottom of the pagethe category “Request”, according to the organization by categoryindicated by notice “view by category”. Each information elementcorresponds, here as well, to a horizontal zone which extends into allzones of the subject involved.

It is observed that the information elements are strictly identical tothose in the table above, except that:

-   -   their order of presentation, in the vertical direction, has been        modified.

the titles have been completed in order to show the complete filiationof each information element, since it is no longer visible in the orderof presentation. File Edition Display Favorite Tools ? SYSTEAM TechnicalManagement DT Report TEST Test Report Object W28 Week 28 From: BRDEVGroup Project Beam Report Notes: View by CATEGORY GLOBAL ML  1. ProjectALPHA General status Δ    This text explains the general status ofproject ALPHA,    from the point of view of ML ML  2. Project BETAGeneral status H    This text explains the general status of projectBETA,    from the point of view of ML JOBS ML  3. Project ALPHA -Development Job 60%    Status: This text explains the progress of thejob    “development” of the project ALPHA ML  4. Project ALPHA -Financing Job 20%    Status: This text explains the progress of the job   “financing” of the project ALPHA ML  5. Project ALPHA - Marketing Job10% ML  6. Project ALPHA - Marketing - Contact Distributor Job  0%   Status: This text explains the progress of the job    “marketing” of theproject ALPHA ML  7. Project BETA - Definition of the Product Job 20%   Status: This text explains the progress of the job    “definition of theproduct” of the project BETA PROBLEMS ML Δ  8. Project ALPHA -Development - Bug in XML PB/Technical  function interface    Impact:This text describes the consequences of the    problem “Bug in the XMLfunction interface” ML □  9. Project ALPHA - Marketing - General delayPB/Resources    This text emphasizes the delay in the marketing jobs,   attributing the cause to the lack of qualified human    resources andspecifies the need to be met REQUESTS ML 10. Project ALPHA -Development - Bug in XML RQ/Meeting Rapp function interface - Use of adifferent supplier?    This text proposes a meeting date to examine aproposal    for a solution to the problem “Bug in XML function   interface” ML □ 11. Project ALPHA - Financing - Start over Devis RQ/ActURG Industrialization    This text states the reason for action demandedfrom the    addressee of the report

Below, a third example is shown of the presentation of the firstdocument shown above in the two previous tables, but re-organized bypriority, as it would appear on a computer screen. This presentation isalways displayed here by an Internet navigation software program. Thedocument contains meta-information, an indication of the organization ofthe presentation of the document, here “view by priority” and elevenzones for giving information elements, the first two, at the top of thepage, involving the highest priority indicated in the fields “Priority”or “Priol” shown in the first table above, the next one, moderatepriority corresponding to notices and the last eight at the bottom ofthe page, the lowest priority, according to the organization by categoryindicated by the notice “view by priority”. Each information elementcorresponds, here as well, to a horizontal zone which extends into allzones of the category involved.

It is observed that the information elements are strictly identical tothose in the table above, but their order of presentation, in thevertical direction, has been modified. File Edition Display FavoriteTools ? SYSTEAM Technical Management DT Report TEST Test Report ObjectW28 Week 28 From: BRDEV Group Project Beam Report Notes: View byPRIORITY CRITICAL ML □  1. Project ALPHA - Marketing - General delayPB/Resources    This text emphasizes the delay in the marketing jobs,   attributing the cause to the lack of qualified human    resources andspecifies the need to be met ML □  2. Project ALPHA - Financing - Startover Devis RQ/Act URG  Industrialization    This text states the reasonfor action demanded from the    addressee of the report NOTICES ML Δ  3.Project ALPHA - Development - Bug in XML PB/Technical  functioninterface    Impact: This text describes the consequences of the   problem “Bug in the XML function interface” ML  4. Project ALPHA Generalstatus Δ    This text explains the general status of project ALPHA,   from the point of view of ML ML  5. Project BETA General status H   This text explains the general status of project BETA,    from the pointof view of ML ML  6. Project ALPHA - Development Job 60%    Status: Thistext explains the progress of the job    “development” of the projectALPHA ML  7. Project ALPHA - Financing Job 20%    Status: This textexplains the progress of the job    “financing” of the project ALPHA ML 8. Project ALPHA - Marketing Job 10% ML  9. Project ALPHA - Marketing -Contact Distributor Job  0%    Status: This text explains the progressof the job    “marketing” of the project ALPHA ML 10. Project BETA -Definition of the Product Job 20%    Status: This text explains theprogress of the job    “definition of the product” of the project BETAML 11. Project ALPHA - Development - Bug in XML RQ/Meeting Rapp functioninterface - Use of a different supplier?    This text proposes a meetingdate to examine a proposal    for a solution to the problem “Bug in XMLfunction    interface”

In the table below, you will observe the same elements as in the secondtable above, with, at the bottom of the page, a summary which onlycontains the titles of the information elements that have a highpriority or “General Status” in the second table above.

The method that is the object of the invention makes it possible toautomatically generate a summary comprised of a selection of informationelements present in condensed form, i.e. without the detailed paragraphof text.

The information elements are selected as a function of the “priority”which is allocated to them by the editor (the presence or not of a“priority” in the summary being defined by the standard). Also, it ispossible to force the appearance of certain “categories” in the summary.File Edition Display Favorite Tools ? SYSTEAM Technical Management DTReport TEST Test Report Object W28 Week 28 From: BRDEV Group ProjectBeam Report Notes: View directly with SUMMARY ML 1.  Project ALPHAGeneral status Δ    This text explains the general status of projectALPHA,    from the point of view of ML ML 1.1 Development Job 60%   Status: This text explains the progress of the job    “development” ofthe project ALPHA ML Δ    > Bug in XML function interface PB/Technical   Impact: This text describes the consequences of the    problem “Bugin the XML function interface” ML      Use of a different supplier?RQ/Meeting Rapp      This text proposes a meeting date to examine a     proposal for a solution to the problem “Bug in      XML functioninterface” ML 1.2 Financing Job 20%    Status: This text explains theprogress of the job    “financing” of the project ALPHA ML □    > Startover Devis Industrialization RQ/Act URG      This text states the reasonfor action demanded      from the addressee of the report ML 1.3Marketing Job 10% ML    > Contact Distributor Job  0%    Status: Thistext explains the progress of the job    “marketing” of the projectALPHA ML □    > General delay PB/Resources    This text emphasizes thedelay in the marketing jobs,    attributing the cause to the lack ofqualified human    resources and specifies the need to be met ML 2. Project BETA General status H    This text explains the general statusof project BETA,    from the point of view of ML ML 2.1 Definition ofthe Product Job 20%    Status: This text explains the progress of thejob    “definition of the product” of the project BETA SUMMARY ML A.Project ALPHA General status Δ ML B. Project ALPHA - Development - Bugin XML RQ/Meeting Rapp function interface - Use of a different supplier?ML □ C. Project ALPHA - Financing - Start over Devis RQ/Act URGIndustrialization ML □ D. Project ALPHA - Marketing - General delayPB/Resources ML E. Project BETA General status H

In the table below, it will be observed a second document, organized bysubject. It will be observed that the standard used for the two examplesof documents consists of a prespecified framework which is limited tothe highest level titles “Project ALPHA” and “Project BETA”, the titlesor labels of the information elements of the lower levels being entirelydefined by the editors. In other examples, several hierarchicallyordered levels of titles or labels can be defined by the standard andcan be modified or not by the editor. File Edition Display FavoriteTools ? SYSTEAM Technical Management DT Report TEST Test Report ObjectW28 Week 28 From: BREXP Group Audit Beam Report Notes: View by SUBJECTPROJECT ALPHA JPL 1.  Project ALPHA General status H    This textexplains the general status of project ALPHA,    from the point of viewof JPL JPL 1.1 Definition of the Product Job 100%    Status: This textexplains the progress of the job    “definition of the product” of theproject ALPHA    according to JPL JPL 1.2 Development Job  50%   Status: This text explains the progress of the job    “development” ofthe project ALPHA according to JPL JPL    > Problem XML interfacePB/Technical      This text explains JPL's solution to the problem     “XML interface” JPL 1.3 Marketing Job  20%    Status: This text explainsthe progress of the job    “marketing” of the project ALPHA according toJPL PROJECT BETA JPL 2.  Project BETA General status H JPL 2.1 MarketingJob  60%    Status: This text explains the progress of the job   “marketing” of the project BETA according to JPL

You will observe, in the table below, the consolidation of the documentsshown in the second and sixth (the previous one) table above. Theinformation elements coming form the first and the second report aresorted and juxtaposed after the title and subtitles which are common tothem.

The method that is the object of the present invention makes it possibleto merge several reports simply by compiling the information elements ofthe different original reports after each title that they have incommon. It is observed that the numbering of the titles or labels isgenerated automatically by the software implementing the method that isthe object of the present invention depending on the effective sequenceof the information elements in a given report. It has only a “visual”role.

The “consolidation” here is a simple juxtaposition of reports. It takeson its full meaning during the sorting (for example, by subject), beingunderstood that when several information elements of several reportshave the same hierarchy of “titles”, they are merged and presented underthis hierarchy of “titles” with a unique number.

Once this consolidation of reports is done, the result can be subjectedto the different processing presented above:

-   -   re-organization (for a consolidation by subject, by category or        by priority),    -   summary (total of the summaries of the original reports),

comparison (relative to a previous consolidation). File Edition DisplayFavorite Tools ? SYSTEAM Technical Management DT Report TEST Test ReportObject W28 Week 28 From: BRDEV Group Project Beam-Report (ML) BREXPGroup Audit Beam Report (JPL) Notes: View by SUBJECT PROJECT ALPHA ML1.  Project ALPHA General status Δ    This text explains the generalstatus of project ALPHA,    from the point of view of ML JPL Generalstatus H    This text explains the general status of project ALPHA,   from the point of view of JPL ML 1.1 Development Job 60%    Status: Thistext explains the progress of the job    “development” of the projectALPHA JPL Job 50%    Status: This text explains the progress of the job   “development” of the project ALPHA according to JPL ML Δ    > Bug inXML function interface PB/Technical    Impact: This text describes theconsequences of the    problem “Bug in the XML function interface” ML     Use of a different supplier? RQ/Meeting Rapp      This textproposes a meeting date to examine a      proposal for a solution to theproblem “Bug in      XML function interface” JPL    > Problem XMLinterface PB/Technical      This text explains JPL's solution to theproblem      “XML interface” ML 1.2 Financing Job 20%    Status: Thistext explains the progress of the job    “financing” of the projectALPHA ML □    > Start over Devis Industrialization RQ/Act URG      Thistext states the reason for action demanded      from the addressee ofthe report JPL 1.3 Definition of the Product Job 100%    Status: Thistext explains the progress of the job    “definition of the product” ofthe project ALPHA    according to JPL ML 1.4 Marketing Job 10% JPL Job20%    Status: This text explains the progress of the job    “marketing”of the project ALPHA according to JPL ML    > Contact Distributor Job 0%   Status: This text explains the progress of the job    “marketing” ofthe project ALPHA ML □    > General delay PB/Resources    This textemphasizes the delay in the marketing jobs,    attributing the cause tothe lack of qualified human    resources and specifies the need to bemet

Below, it will be found an eighth example for presentation of a documentsummarizing the first document shown above in the previous tables,containing only the information of the highest or average priority, asit would appear on a computer screen. This presentation is alwaysdisplayed here by an Internet navigation software program. The documentcontains meta-information, an indication of the organization of thepresentation of the document, here “summarizing” and three zones forgiving information elements, the first two involving the highestpriority indicated in the fields “Priority” or “Priol” shown in thefirst table above, and the last one involving the average priority levelindicated in the same fields according to the organization by categoryindicated in the same field, conforming to the organization by categoryindicated by the notice “view by priority Each information elementcorresponds, here as well, to a horizontal zone which extends into allzones of the category involved.

It is observed that the information elements are strictly identical tothose in the table above, but their number has been modified in order toonly retain the information relating to the high or average priorities.File Edition Display Favorite Tools ? SYSTEAM Technical Management DTReport TEST Test Report Object W28 Week 28 From: BRDEV Group ProjectBeam-Report (ML) Notes: SUMMARY PROJECT ALPHA CRITICAL ML □ 1. ProjectALPHA - Marketing - General delay PB/Resources    This text emphasizesthe delay in the marketing jobs,    attributing the cause to the lack ofqualified human    resources and specifies the need to be met ML □ 2.Project ALPHA - Financing - Start over Devis RQ/Act URGIndustrialization    This text states the reason for action demandedfrom the    addressee of the report NOTICES ML Δ 3. Project ALPHA -Development - Bug in XML PB/Technical function interface    Impact: Thistext describes the consequences of the    problem “Bug in the XMLfunction interface”    This text explains JPL's solution to the problem   “XML interface”

The method that is the object of the invention thus makes it possible tostandardize the content and the form of the reporting documents, to makeeasier their development and their use, and in the end, to improve theeffectiveness of this communication.

You will observe that the function of creating a summary can be doneover criteria other than the priority, as indicated above, and allows,for example, creation immediately at the end of a meeting of a meetingreport having, for example, only the information relating to the actionsand the decisions, while keeping the content of the proceedingsavailable during the meeting.

A comparison function makes it possible to compare the information ofdifferent documents according to the same standard, by comparing theinformation that corresponds to the same titles. This comparison thusmakes it possible to assess the differences between points of view ofdifferent authors of the reports and/or between successive reports thatcome from the same author.

In a preferred embodiment mode, the implementation of the method that isthe object of the invention thus provides the following solutions:Problem, requirement Solution Cost of training, Natural ergonomics of atext processor; acceptability gets rid of visual formatting forfunctions Cost of inputting and The tool provides all formattingservices formatting (heading, indentation, numbering, page layout)Heterogeneity, lack of Implementation of standards, completeness, riskof wrong personalizable, contains both a inputting interpretation helpand a content guide Fear of restrictive Light standards, easy to modify,non- or heavy standards locking, and always the possibility of a free(dread of forms) expression for what “doesn't fit in the cases.”Differences in points of Automatic functions of re-organization, viewmaking it possible to present a given content from several points ofview (by subject, by category, by importance . . . ) Chronologicalmonitoring Function for automatic comparison between two reports, withhighlighting of the modifications Consolidation of several Function forautomatic combination of reports several reports, with connections bysubject. Help in synthesis on Automatic generation of “summaries”, oneor more reports according to personalizable criteria (defined in thestandard)

Other functions of the method that is the object of the invention areexplained below but are not shown. The method that is the object of theinvention can automatically display the differences between the currentreport and a reference report, on the basis of the “titles” of theinformation elements.

For each information element common to the two reports, the method showsthe differences found on the fields other than the “title”. It is notedthat the absence of any difference over the entire text following atitle is considered a priori as suspect, and is highlighted, forexample, by automatic underlining. It is observed that this function canserve the editor as well as the addressee of the report: it can beactivated continuously during the development of a report, allowing theeditor to work in an incremental manner on the basis of his previousreport.

The method that is the object of the invention has a hybrid character,being both a text editor and a database interface: the document managedis greatly structured, but the user sees it as a linear text (includingduring its development), and functions of a traditional text processingapply to it, which makes it very user-friendly and easy to use.

In FIG. 1, a step 800 is observed for defining a document standard whichdetermines the general framework of the document in the form of a seriesof titles and/or conventional meanings and authorized values of certainnotable information fields, as indicated above. During the step 800, forat least one title, a selection step is defined in the standard if thetitle can be modified by a user and the categories of information aredefined. Later, the user and sender (called the “first” user) performs astep 802 for selecting a document standard to prepare the document. Thisselection can be done indirectly in selecting a document made inimplementing the method that is the object of the invention. Thestandard itself appears as a document. Then, the user and senderperforms step 804 for selecting information of the document and thestandard.

During a step 806, it is determined whether, in the standard, theinformation selected can be edited (for example, a title or aninformation field called “notable”, for example, information aboutcategory, percentage, priority). If the information selected iseditable, a step 808 for editing the information by a complement (text,percentage, icon, context, including the parts of the standard that areeditable for example) or by selecting a value for the notable field.During step 808, in at least one text zone, the titles defined by thestandard and the text input by the user appear, like a single lineartext, to be shown in the second to the seventh tables above. During step808, the user/sender can modify the level of priority associated withthe information input (by default, each information element is linked tothe lowest priority level). During step 808, the program implementingthe method that is the object of the invention automatically links (orafter an identity request) an identification of the author to theinformation input.

Then one determines, during a determination step 810, if otherinformation is selected. If yes, step 806 is re-started. If no, duringstep 812, one determines whether the user/sender demanded a transmissionof the document to at least one user/addressee. If yes, the programperforms a step 814 for transmission of information of the document tothe at least one user/addressee (called “second user”) during which onetransmits preferentially the information of the document according to anaccessible page format over an information network, for example, byusing Internet navigator.

When the document has been received by a user/addressee, when thedocument is opened by this user/addressee, his computer performs a step816 for reconstructing the document, by making a possible call to thedocument standard stored locally by this computer or remotely on anothercomputer.

During step 818, one determines if the user/addressee has demanded aconsolidation of documents. If no, step 822 is performed. If theconsolidation demand is determined, during a step 820, theuser/addressee selects at least one other document and the programimplementing the method that is the object of the invention performs theconsolidation of the document transmitted and each document selected.During this consolidation of documents, one juxtaposes under one uniquetitle the information of the documents which are linked to the identicaltitles (i.e. the same order of titles and sub-titles, for example, inthe seventh table “project alpha/development”) in the differentdocuments to be consolidated.

Next, the program determines, during step 822, if a request forre-organization, summarization or comparison has been made by theuser/addressee. If no, step 826 is performed. If it is determined that aprocessing of the document is requested during step 822, the programperforms step 824 for performing a requested processing as explainedabove. In order to determine a summary of the document, one selects theinformation depending on a hierarchy of information values, title level(for example, only the first level), notable information values (forexample, priority or important categories). For the re-organization,during the selection step, you can select a hierarchy of informationvalues depending on priorities, categories, or identifications of theauthors of the documents.

Finally, the program performs step 826 to supply the document, forexample, display or printing, according to the user/addressee'sselection. As indicated above, in at least one text zone, the titlesdefined by the standard and the text input by the user appear as asingle linear text.

It is noted that, during step 822, the user/sender selects a sortingcriterion based on the document titles or on the notable fields.

Of course, the user/sender can perform the same consolidation,re-organization, selection of summary as the second user, and the seconduser can in turn modify the document transmitted or the documentsupplied. Though only a single supply operation is indicated, during thedifferent steps, the user involved will see on his screen the documentwhile it is processed.

It is understood that the implementation of the present inventionincreases the speed of creation, transmission, comprehension andprocessing of reports and thus of the supervision of the humanorganization which produces them, while increasing the readability orexploitability of these reports. These technical results are all themore important since the content of the reports are, totally orpartially, reported in other reports, for example, in going up thehierarchical levels.

1. Method for communicating structured information, between a first userand at least one second user, said method comprising: defining adocument standard determining a general framework of the documentcomprised of: a series of titles and/or conventional notifications; andvalues authorized by certain fields of noteworthy information; inputtingby the first user, information to be provided incorporating steps ofinputting text and/or titles as a supplement to the general frameworkand/or selecting values authorized on the apparent fields; transmittingthe information of the document from the first user to the destinationof each secondary user; selecting by each secondary user, a sortingcriterion based on the titles or the noteworthy fields of the document;re-organizing the document according to the selected criteria; andsupplying, to the secondary user, the document re-organized according tothe criterion.
 2. Method according to claim 1, wherein, during the stepfor inputting and/or during the step for supplying, in at least one textzone, the titles defined by the standard and the text input by the userappear, like a single linear text relating to the traditional ergonomicsof text processing.
 3. Method according to claim 1, wherein, during thestep for defining the standard, for at least one title, a selection stepis made if the title can be modified by the first user during theinputting step.
 4. Method according to claim 1, wherein, during the stepfor inputting of the information, the first user can modify at least onepart of the standard defined during the step for definition of thestandard.
 5. Method according to claim 1, wherein, during the step fordefining the standard, categories of information are defined and, duringthe selection step, one can select a hierarchy of information valuesdepending on the categories.
 6. Method according to claim 1, wherein,during the step for inputting of the information, a priority level isassociated with the information input, and, during the selection step,one can select a hierarchy of information values depending on thepriorities.
 7. Method according to claim 1, wherein, during the step fortransmission, the information of the document is transmitted accordingto an accessible page format over an information network, readable usinga web navigator and printable from any office work station equipped witha web navigator and a printer.
 8. Method according to claim 1, saidmethod further comprising: consolidating documents, during which theinformation of the documents which are linked to the same titles arejuxtaposed under a unique title into the different documents to beconsolidated.
 9. Method according to claim 1, said method furthercomprising: determining a summary of the document, during whichinformation is selected as a function of a hierarchy of informationvalues.
 10. Method according to claim 1, wherein, during the step forinputting information, an identification of the author of theinformation input is allocated, and during the selection step, one canselect a hierarchy of information values depending on theidentifications.
 11. Method according to claim 1, wherein, during thestep for supplying to the second user of the document reorganizedaccording to the criterion, the document contains all of the titles ofthe document and information input by the first user.
 12. Device forcommunicating structured information between a first user and at leastone second user, said device comprising: a means for semanticallydefining a document standard (800), which is suitable for determining ageneral framework of the document comprised of: a series of titlesand/or conventional notifications; and values authorized by certainfields of noteworthy information; a means for inputting, in the firstuser terminal, information to be provided by inputting text and/ortitles as a supplement to the general framework and/or by selectingvalues authorized on the apparent fields; a means for transmitting theinformation of the document from the first user terminal to thedestination of each secondary user terminal; a means for selecting, ineach secondary user terminal, a sorting criterion based on the titles orthe apparent fields of the document; a means for re-organization of thedocument according to the selected criteria by the selection mechanism;and a means for supplying, by each second user terminal, the documentre-organized according to the criterion and containing all of the titlesof the document and the information input by the first user.